Merged
Conversation
btbest
force-pushed
the
release-1.4.2b5
branch
from
cb599b8 to
ecd5b5d
Compare
k-dominik
reviewed
Nov 7, 2025
Contributor
k-dominik
left a comment
k-dominik
left a comment
There was a problem hiding this comment.
I would probably also mention the performance improvements introduced in ilastik/volumina#339 as it makes quite the difference on how ilastik feels. Unless of course the new version of volumina is not it (which it should).
Comment on lines
+98
to
+102
| <ul> | ||
| <li>* Physical pixel size metadata is now carried over from inputs to exports when using TIFF or H5</li> | ||
| <li>* Pixel label explorer: Easily find and jump to previously drawn brush strokes</li> | ||
| <li>* New "multi-scale OME-Zarr" export format and better UX when adding multiscale datasets to a project</li> | ||
| <li>* New variant of Object Classification workflow, using a label image as the second input</li> |
Contributor
There was a problem hiding this comment.
Suggested change
| <ul> | |
| <li>* Physical pixel size metadata is now carried over from inputs to exports when using TIFF or H5</li> | |
| <li>* Pixel label explorer: Easily find and jump to previously drawn brush strokes</li> | |
| <li>* New "multi-scale OME-Zarr" export format and better UX when adding multiscale datasets to a project</li> | |
| <li>* New variant of Object Classification workflow, using a label image as the second input</li> | |
| <ul> | |
| <li> Physical pixel size metadata is now carried over from inputs to exports when using TIFF or H5</li> | |
| <li> Pixel label explorer: Easily find and jump to previously drawn brush strokes</li> | |
| <li> New "multi-scale OME-Zarr" export format and better UX when adding multiscale datasets to a project</li> | |
| <li> New variant of Object Classification workflow, using a label image as the second input</li> |
no need for markers in <li>
Contributor
Author
There was a problem hiding this comment.
and no need for the leading space ;)
btbest
force-pushed
the
release-1.4.2b5
branch
from
ecd5b5d to
b131c50
Compare
Contributor
Author
|
oh yeah definitely! I was sure I was gonna forget things, so I just went through the PRs. And of course forgot things because of that. |
btbest
force-pushed
the
release-1.4.2b5
branch
from
b131c50 to
013fda8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No notes section for now because I'm not aware of anything in addition to the existing 1.4.1 notes.